Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 055017242bc975f080ee396c8edd945dd66fd08d7c011fa969ad4e518a02e4b6

Tx prefix hash: c75351959d11c068d57b1c93323f6f70382f6b578af9afa51c0e97b58e85dc93
Tx public key: cfb550e2f425f8ba0779f638741516ee09e119a37e7e228a84a1dbbaf7540dc6
Timestamp: 1736235832 Timestamp [UCT]: 2025-01-07 07:43:52 Age [y:d:h:m:s]: 00:295:21:13:33
Block: 1192031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208960 RingCT/type: yes/0
Extra: 01cfb550e2f425f8ba0779f638741516ee09e119a37e7e228a84a1dbbaf7540dc60211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1795b78d4755c9f712c298f0d8d015f9806715c0c7d6679e32647bf5d4c5981d 0.600000000000 1678576 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": 1192041, "vin": [ { "gen": { "height": 1192031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1795b78d4755c9f712c298f0d8d015f9806715c0c7d6679e32647bf5d4c5981d" } } ], "extra": [ 1, 207, 181, 80, 226, 244, 37, 248, 186, 7, 121, 246, 56, 116, 21, 22, 238, 9, 225, 25, 163, 126, 126, 34, 138, 132, 161, 219, 186, 247, 84, 13, 198, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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