Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2acfdb986797cc1fae48dae856d28c0a50e3997619d43062d8c1528923785c5

Tx prefix hash: 1b09a6ca8932f8ec3a2e437881da4eb65edaf3d613b9dc950718d648e1957d01
Tx public key: f7384ad67be8d6f0b5facbbe021ccd4e871248c1e7bea58d603dba09579dbceb
Timestamp: 1706683534 Timestamp [UCT]: 2024-01-31 06:45:34 Age [y:d:h:m:s]: 01:141:01:11:27
Block: 947137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361778 RingCT/type: yes/0
Extra: 01f7384ad67be8d6f0b5facbbe021ccd4e871248c1e7bea58d603dba09579dbceb0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2d0cd8f2bb408037afcb4926f3e5f55ff1761e64bcf1036e68cc8802f82f185 0.600000000000 1405485 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": 947147, "vin": [ { "gen": { "height": 947137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2d0cd8f2bb408037afcb4926f3e5f55ff1761e64bcf1036e68cc8802f82f185" } } ], "extra": [ 1, 247, 56, 74, 214, 123, 232, 214, 240, 181, 250, 203, 190, 2, 28, 205, 78, 135, 18, 72, 193, 231, 190, 165, 141, 96, 61, 186, 9, 87, 157, 188, 235, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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