Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d9a31d94e44de98f5df44d68d7cd96bc6fdbcf93dbcbe5c7c94aae85a4f1caa

Tx prefix hash: 1fc414b11a3ae07e02626dd4c8f6a16ad483ba46991b9d4065f6abc36c16e8aa
Tx public key: bf3b65beeb4f29bbb1271d99f79577b6c4256da163483b8ec8b7d33f745a9d10
Timestamp: 1762167317 Timestamp [UCT]: 2025-11-03 10:55:17 Age [y:d:h:m:s]: 00:056:13:17:02
Block: 1404015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40492 RingCT/type: yes/0
Extra: 01bf3b65beeb4f29bbb1271d99f79577b6c4256da163483b8ec8b7d33f745a9d100211000000085dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a5a5eb645bffdc0a81d9f0c95aafd4e9b014c83601c3cfffc7dab4b2c1b938f 0.600000000000 1892372 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": 1404025, "vin": [ { "gen": { "height": 1404015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a5a5eb645bffdc0a81d9f0c95aafd4e9b014c83601c3cfffc7dab4b2c1b938f" } } ], "extra": [ 1, 191, 59, 101, 190, 235, 79, 41, 187, 177, 39, 29, 153, 247, 149, 119, 182, 196, 37, 109, 161, 99, 72, 59, 142, 200, 183, 211, 63, 116, 90, 157, 16, 2, 17, 0, 0, 0, 8, 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