Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7db9ee730653abac563a0dc516d57b56e4f158033f7aa03f71c32fdfdef987

Tx prefix hash: 3d6f995950098f2c55ba08c49663c87f80392ec7fc17b4863eb2e62ecdf1ee53
Tx public key: 84e6f658f2e2160a6eb66f53780fac834aa66cd8cb4dc29b12202aa5226c11dd
Timestamp: 1711274818 Timestamp [UCT]: 2024-03-24 10:06:58 Age [y:d:h:m:s]: 01:053:16:40:58
Block: 985235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299366 RingCT/type: yes/0
Extra: 0184e6f658f2e2160a6eb66f53780fac834aa66cd8cb4dc29b12202aa5226c11dd02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0410ad5687f0f51ea55d3af27af168c72ba5670dce875f7e75864abb5c4fb9f8 0.600000000000 1445444 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": 985245, "vin": [ { "gen": { "height": 985235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0410ad5687f0f51ea55d3af27af168c72ba5670dce875f7e75864abb5c4fb9f8" } } ], "extra": [ 1, 132, 230, 246, 88, 242, 226, 22, 10, 110, 182, 111, 83, 120, 15, 172, 131, 74, 166, 108, 216, 203, 77, 194, 155, 18, 32, 42, 165, 34, 108, 17, 221, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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