Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35e47eff1ce479982990b5279edfc19bdcbc3f96eb33fe66073ed2ccaf70d076

Tx prefix hash: 4087552b3dcfac804a1ee848e346430d4a80964e8c94b5abb3f4564e43f14a31
Tx public key: 863f8134fdd8b9f783c61ae1753a032eab8bd2d0db34f34c33b0de5900dd1c45
Timestamp: 1724958057 Timestamp [UCT]: 2024-08-29 19:00:57 Age [y:d:h:m:s]: 00:238:19:02:32
Block: 1098656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170545 RingCT/type: yes/0
Extra: 01863f8134fdd8b9f783c61ae1753a032eab8bd2d0db34f34c33b0de5900dd1c4502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e8ea1478fa55e5e84dfac6d9fce4474c2fd6f68fa2fd442aa2fe96f55dbfca0 0.600000000000 1574447 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": 1098666, "vin": [ { "gen": { "height": 1098656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e8ea1478fa55e5e84dfac6d9fce4474c2fd6f68fa2fd442aa2fe96f55dbfca0" } } ], "extra": [ 1, 134, 63, 129, 52, 253, 216, 185, 247, 131, 198, 26, 225, 117, 58, 3, 46, 171, 139, 210, 208, 219, 52, 243, 76, 51, 176, 222, 89, 0, 221, 28, 69, 2, 17, 0, 0, 0, 1, 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