Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 110bbb613fa9783f5f289d7272edd2c4bded119679b27946c10d40cdad71b375

Tx prefix hash: fd9db6d1c41f3928801142c79e79dc4f0971873d815fdb7dd63e8dcb30fa6b1c
Tx public key: f03e99cc1cc6a9ce4731c5420ba911a1beb9dd02ae112311fbae5aecfc1858da
Timestamp: 1728945577 Timestamp [UCT]: 2024-10-14 22:39:37 Age [y:d:h:m:s]: 01:025:07:10:15
Block: 1131720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276442 RingCT/type: yes/0
Extra: 01f03e99cc1cc6a9ce4731c5420ba911a1beb9dd02ae112311fbae5aecfc1858da021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1192bf125fe17a628efe9a3f2b8a2bbdfb3846d94a9f520acce3502cbe710c6c 0.600000000000 1614625 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": 1131730, "vin": [ { "gen": { "height": 1131720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1192bf125fe17a628efe9a3f2b8a2bbdfb3846d94a9f520acce3502cbe710c6c" } } ], "extra": [ 1, 240, 62, 153, 204, 28, 198, 169, 206, 71, 49, 197, 66, 11, 169, 17, 161, 190, 185, 221, 2, 174, 17, 35, 17, 251, 174, 90, 236, 252, 24, 88, 218, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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