Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff8709fdf9d7ff62c67651783d04e2cfdb64705e8dde202dcedbb03c7fa9c76a

Tx prefix hash: 6e2f35a67bc4e881d5d592ebdf0acc6d5a4e1c8e000a19d37b60ddbb860f0106
Tx public key: 2b3dbba3bf9cf4c0427ace8ac72c3e1ef5b0198d593ed53873a6906745e6d92f
Timestamp: 1738972662 Timestamp [UCT]: 2025-02-07 23:57:42 Age [y:d:h:m:s]: 00:324:05:46:15
Block: 1214417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229552 RingCT/type: yes/0
Extra: 012b3dbba3bf9cf4c0427ace8ac72c3e1ef5b0198d593ed53873a6906745e6d92f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c3daef819543f66329674fa1811a3075d01de557beba8ea0faa255f4d0fd4f0 0.600000000000 1701208 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": 1214427, "vin": [ { "gen": { "height": 1214417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c3daef819543f66329674fa1811a3075d01de557beba8ea0faa255f4d0fd4f0" } } ], "extra": [ 1, 43, 61, 187, 163, 191, 156, 244, 192, 66, 122, 206, 138, 199, 44, 62, 30, 245, 176, 25, 141, 89, 62, 213, 56, 115, 166, 144, 103, 69, 230, 217, 47, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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