Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23d2a6740071b6000c31ab6f9b4ccf9afafc71dab4b396197b1d1a9f315250a2

Tx prefix hash: bc88ea309dd560a5ec37916e50c8ba6d388205ceb4f609beab9ed379b3b5f7e4
Tx public key: 3ee3706dcd85d13a2a2f34fa88aad5122d9dac9cf677747dbe7f88684a421c4f
Timestamp: 1705852995 Timestamp [UCT]: 2024-01-21 16:03:15 Age [y:d:h:m:s]: 01:329:22:38:49
Block: 940246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494664 RingCT/type: yes/0
Extra: 013ee3706dcd85d13a2a2f34fa88aad5122d9dac9cf677747dbe7f88684a421c4f02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f904962024f1710f127701728843e336f6d37c956c031796080c7d98e2ea2d9 0.600000000000 1398380 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": 940256, "vin": [ { "gen": { "height": 940246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f904962024f1710f127701728843e336f6d37c956c031796080c7d98e2ea2d9" } } ], "extra": [ 1, 62, 227, 112, 109, 205, 133, 209, 58, 42, 47, 52, 250, 136, 170, 213, 18, 45, 157, 172, 156, 246, 119, 116, 125, 190, 127, 136, 104, 74, 66, 28, 79, 2, 17, 0, 0, 0, 8, 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