Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ef4dffff7f008d62172d2e20ae7422a87239b8e9a307c8499e3b80da9dc2deb

Tx prefix hash: 066a7d3fba547ba55a0b2362a8fa793eedfcc8f827d871f77f2cc4063e4cfe35
Tx public key: efccfe4cb05fd17b6cf621edbf7913bd9fa7e52c4606e52595a1501579906864
Timestamp: 1760104617 Timestamp [UCT]: 2025-10-10 13:56:57 Age [y:d:h:m:s]: 00:038:02:44:40
Block: 1386926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27284 RingCT/type: yes/0
Extra: 01efccfe4cb05fd17b6cf621edbf7913bd9fa7e52c4606e52595a150157990686402110000000697baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1db21d8481a1ae5f07a9c12753ef043eb22918c56c9774fb138a1c731a1a1ead 0.600000000000 1875107 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": 1386936, "vin": [ { "gen": { "height": 1386926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1db21d8481a1ae5f07a9c12753ef043eb22918c56c9774fb138a1c731a1a1ead" } } ], "extra": [ 1, 239, 204, 254, 76, 176, 95, 209, 123, 108, 246, 33, 237, 191, 121, 19, 189, 159, 167, 229, 44, 70, 6, 229, 37, 149, 161, 80, 21, 121, 144, 104, 100, 2, 17, 0, 0, 0, 6, 151, 186, 249, 34, 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