Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 481ed18221feabbac3a132846c14e829fea71f7d44cc998d1b265e0afbcd2ddd

Tx prefix hash: 75b9f2eb6ced646ae8dad56e473cbdf3aafc0a4d40ae1a1492403e62604a7379
Tx public key: bb3c6057f6b51db2f519baaedf51a181d5af5fe24ec10bf279537baa0935928d
Timestamp: 1725146675 Timestamp [UCT]: 2024-08-31 23:24:35 Age [y:d:h:m:s]: 01:060:12:42:54
Block: 1100221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301696 RingCT/type: yes/0
Extra: 01bb3c6057f6b51db2f519baaedf51a181d5af5fe24ec10bf279537baa0935928d02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01a5bc9be89f9d5c03e13d88f6687445373815094e3de01e54f14dfc2e5a9dc0 0.600000000000 1576194 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1100231, "vin": [ { "gen": { "height": 1100221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01a5bc9be89f9d5c03e13d88f6687445373815094e3de01e54f14dfc2e5a9dc0" } } ], "extra": [ 1, 187, 60, 96, 87, 246, 181, 29, 178, 245, 25, 186, 174, 223, 81, 161, 129, 213, 175, 95, 226, 78, 193, 11, 242, 121, 83, 123, 170, 9, 53, 146, 141, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8