Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7084a257c86bb1eeb3f02d49edf34ab755b4622ec67ddd8579a1ef3f90e4ae71

Tx prefix hash: cad0be5ec7361723ed16faabb6c473fdec0258f764ac013606019b3e9c0122d0
Tx public key: 497d54032f328cabfa011a04c3f4dcf2627b7ea6d79fa9a3a48b18151336e47b
Timestamp: 1703805336 Timestamp [UCT]: 2023-12-28 23:15:36 Age [y:d:h:m:s]: 01:105:17:40:25
Block: 923292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336686 RingCT/type: yes/0
Extra: 01497d54032f328cabfa011a04c3f4dcf2627b7ea6d79fa9a3a48b18151336e47b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d76b0453dd9c236739ba5e1aaded6157a6309f6226d0d2ae868331ab6d0d70a5 0.600000000000 1381020 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": 923302, "vin": [ { "gen": { "height": 923292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d76b0453dd9c236739ba5e1aaded6157a6309f6226d0d2ae868331ab6d0d70a5" } } ], "extra": [ 1, 73, 125, 84, 3, 47, 50, 140, 171, 250, 1, 26, 4, 195, 244, 220, 242, 98, 123, 126, 166, 215, 159, 169, 163, 164, 139, 24, 21, 19, 54, 228, 123, 2, 17, 0, 0, 0, 1, 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