Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b01e272c9770a1df2693a7f4f976066994fe747618381af432eab929f8160ed

Tx prefix hash: 70d253109009baac13178780b1c2dc3a5057a5045685b9be060ad2e753b92fec
Tx public key: 7ec93488cbd61d8aa2e3ff666e31b16c23d082c47f0521a3f1973c8eca7cb0b0
Timestamp: 1737149316 Timestamp [UCT]: 2025-01-17 21:28:36 Age [y:d:h:m:s]: 00:152:03:02:31
Block: 1199584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108424 RingCT/type: yes/0
Extra: 017ec93488cbd61d8aa2e3ff666e31b16c23d082c47f0521a3f1973c8eca7cb0b0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d6ccd1625c6a741f0e54616a1a27399e4ef56089efe0350bf455aa56535be4d 0.600000000000 1686217 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": 1199594, "vin": [ { "gen": { "height": 1199584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d6ccd1625c6a741f0e54616a1a27399e4ef56089efe0350bf455aa56535be4d" } } ], "extra": [ 1, 126, 201, 52, 136, 203, 214, 29, 138, 162, 227, 255, 102, 110, 49, 177, 108, 35, 208, 130, 196, 127, 5, 33, 163, 241, 151, 60, 142, 202, 124, 176, 176, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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