Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3be515ba9f6603c8e8907719c807b628df39b95d9d9d2a0cd79de533f436166

Tx prefix hash: e1b586c68056155a5cc24ada45952ba753ccdee755ed7a53670981dc336e6272
Tx public key: bcb8148775bf7510642ae2e3a8c64087d847004783afe2d06a2f4ead320f0e61
Timestamp: 1757760604 Timestamp [UCT]: 2025-09-13 10:50:04 Age [y:d:h:m:s]: 00:109:11:22:10
Block: 1367497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78387 RingCT/type: yes/0
Extra: 01bcb8148775bf7510642ae2e3a8c64087d847004783afe2d06a2f4ead320f0e61021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ba9e87f9b3339e70842b9f422713b4d7f8e522cd87aa685384fb7a8973e3cf7 0.600000000000 1855536 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": 1367507, "vin": [ { "gen": { "height": 1367497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ba9e87f9b3339e70842b9f422713b4d7f8e522cd87aa685384fb7a8973e3cf7" } } ], "extra": [ 1, 188, 184, 20, 135, 117, 191, 117, 16, 100, 42, 226, 227, 168, 198, 64, 135, 216, 71, 0, 71, 131, 175, 226, 208, 106, 47, 78, 173, 50, 15, 14, 97, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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