Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d495617a72d8708b7af2741b01cbbf41ded0374de5941d6c67b1f92349864b0

Tx prefix hash: cb0c56598bcfd44e9642d89bb951ae462538a7081ed054a2ca581ae335b953e5
Tx public key: 84e93e169a128755f2a3b68372a64748038a76d806d9c765061326d1197e4a70
Timestamp: 1695949213 Timestamp [UCT]: 2023-09-29 01:00:13 Age [y:d:h:m:s]: 01:190:07:42:42
Block: 858366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397075 RingCT/type: yes/0
Extra: 0184e93e169a128755f2a3b68372a64748038a76d806d9c765061326d1197e4a7002110000000875e3f0e9000000000000000000

1 output(s) for total of 0.878773924000 dcy

stealth address amount amount idx
00: a53a19eaaa56419ff6c5e0c3393d1f279981c237d1a94732386156b90cc26e3d 0.878773924000 1312538 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": 858376, "vin": [ { "gen": { "height": 858366 } } ], "vout": [ { "amount": 878773924, "target": { "key": "a53a19eaaa56419ff6c5e0c3393d1f279981c237d1a94732386156b90cc26e3d" } } ], "extra": [ 1, 132, 233, 62, 22, 154, 18, 135, 85, 242, 163, 182, 131, 114, 166, 71, 72, 3, 138, 118, 216, 6, 217, 199, 101, 6, 19, 38, 209, 25, 126, 74, 112, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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