Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b58a8be33352c6eed4ab9ddda3262d5cb09fe8d72b094bb80f2f87dc21343004

Tx prefix hash: 854041fc17c200189ff4f54d1e03a8819d27c4d15cc6dd67c60b9974d7155f8e
Tx public key: 11671aa166e54b864b9f6ad792b669ebfb3ddbde902c80945e079c584d20e95c
Timestamp: 1755171010 Timestamp [UCT]: 2025-08-14 11:30:10 Age [y:d:h:m:s]: 00:052:13:53:10
Block: 1346630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37051 RingCT/type: yes/0
Extra: 0111671aa166e54b864b9f6ad792b669ebfb3ddbde902c80945e079c584d20e95c021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a38b38eedc431bd86df86e26c9e705c7db2c763114da9a842c21dea6494f182 0.600000000000 1834531 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": 1346640, "vin": [ { "gen": { "height": 1346630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a38b38eedc431bd86df86e26c9e705c7db2c763114da9a842c21dea6494f182" } } ], "extra": [ 1, 17, 103, 26, 161, 102, 229, 75, 134, 75, 159, 106, 215, 146, 182, 105, 235, 251, 61, 219, 222, 144, 44, 128, 148, 94, 7, 156, 88, 77, 32, 233, 92, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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