Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4813d24c2cac2dfd92ca4e56f1a75f66c105f10f3d93f2a42ce6decb6958043c

Tx prefix hash: c3ce3fce487ebf5f0005647b077aed18d3a4afa7c73ba79d039a1193620012f3
Tx public key: 0eafd50ee2ba7a9623776623c6e11ce4aead2e25c7d002aae0e32d4b372eccaa
Timestamp: 1696551672 Timestamp [UCT]: 2023-10-06 00:21:12 Age [y:d:h:m:s]: 01:113:09:03:57
Block: 863352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342267 RingCT/type: yes/0
Extra: 010eafd50ee2ba7a9623776623c6e11ce4aead2e25c7d002aae0e32d4b372eccaa02110000000133af99f4000000000000000000

1 output(s) for total of 0.845972930000 dcy

stealth address amount amount idx
00: b971a890b7e4141adae1b449893bb8bd584efbcd88334c9f80ef1d1dfd10786f 0.845972930000 1317804 of 0

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": 863362, "vin": [ { "gen": { "height": 863352 } } ], "vout": [ { "amount": 845972930, "target": { "key": "b971a890b7e4141adae1b449893bb8bd584efbcd88334c9f80ef1d1dfd10786f" } } ], "extra": [ 1, 14, 175, 213, 14, 226, 186, 122, 150, 35, 119, 102, 35, 198, 225, 28, 228, 174, 173, 46, 37, 199, 208, 2, 170, 224, 227, 45, 75, 55, 46, 204, 170, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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