Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb8886170e85170663bd8836c61b7939ed2dbaa19dee0d616899116e26122ead

Tx prefix hash: c98d8c4b078b714fc39bf11b9d019c434f0cf0330c79fb5b1cda30df83b930fa
Tx public key: f3c87558898453568822b4c01e5d218d38b7e42a7c0a237e261593e50f2562d9
Timestamp: 1725494906 Timestamp [UCT]: 2024-09-05 00:08:26 Age [y:d:h:m:s]: 00:270:15:58:35
Block: 1103109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193337 RingCT/type: yes/0
Extra: 01f3c87558898453568822b4c01e5d218d38b7e42a7c0a237e261593e50f2562d902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21b47be3462dc4ca087329aed23a44ed7e142695d1ac92bdceca4f12f3270cb9 0.600000000000 1579810 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": 1103119, "vin": [ { "gen": { "height": 1103109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21b47be3462dc4ca087329aed23a44ed7e142695d1ac92bdceca4f12f3270cb9" } } ], "extra": [ 1, 243, 200, 117, 88, 137, 132, 83, 86, 136, 34, 180, 192, 30, 93, 33, 141, 56, 183, 228, 42, 124, 10, 35, 126, 38, 21, 147, 229, 15, 37, 98, 217, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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