Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de9b0b2d763e1d99d2ca8a5909647219e57471ff55a9090e220f4b8a130f2c3a

Tx prefix hash: 747a289a19bf9222c2039343caa0a2708f191dd0a81e514d02085add58953fc1
Tx public key: 967506e673065cfe37839bb3c939e63d43706d6964e2c4e9adf8fa206bcc33ad
Timestamp: 1747568839 Timestamp [UCT]: 2025-05-18 11:47:19 Age [y:d:h:m:s]: 00:219:15:15:12
Block: 1285574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154718 RingCT/type: yes/0
Extra: 01967506e673065cfe37839bb3c939e63d43706d6964e2c4e9adf8fa206bcc33ad0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21abee49cb316c78d7b0dda05b3189c2efb24dfbc2b964a73bf13a57e85f81d0 0.600000000000 1773039 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": 1285584, "vin": [ { "gen": { "height": 1285574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21abee49cb316c78d7b0dda05b3189c2efb24dfbc2b964a73bf13a57e85f81d0" } } ], "extra": [ 1, 150, 117, 6, 230, 115, 6, 92, 254, 55, 131, 155, 179, 201, 57, 230, 61, 67, 112, 109, 105, 100, 226, 196, 233, 173, 248, 250, 32, 107, 204, 51, 173, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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