Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ff8c964bdd0d1988e5b8a12287aa82c48ba58a66105d2c624979f8af47d969

Tx prefix hash: d7b41974634650b89213c69a1378d65eac700a7599c6985a24ac43bafacd8e45
Tx public key: 1f61cbae9f581cafb6ca6ea20925db12fcebae13a8b5be73ed592c352d328a89
Timestamp: 1761865617 Timestamp [UCT]: 2025-10-30 23:06:57 Age [y:d:h:m:s]: 00:009:20:33:56
Block: 1401536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7047 RingCT/type: yes/0
Extra: 011f61cbae9f581cafb6ca6ea20925db12fcebae13a8b5be73ed592c352d328a890211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e095e5ab42b8d8371cfab638fa3f79e97d22390ea539b002f237bf452a1ea6f2 0.600000000000 1889855 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": 1401546, "vin": [ { "gen": { "height": 1401536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e095e5ab42b8d8371cfab638fa3f79e97d22390ea539b002f237bf452a1ea6f2" } } ], "extra": [ 1, 31, 97, 203, 174, 159, 88, 28, 175, 182, 202, 110, 162, 9, 37, 219, 18, 252, 235, 174, 19, 168, 181, 190, 115, 237, 89, 44, 53, 45, 50, 138, 137, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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