Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d191388862b0bd4715bf24a9a98051cb7d510394e601628b36450ed81a43fa7d

Tx prefix hash: 5d21673b13b32d3404089acf4505f9af4d4a87c84a0493a91e98b93870fa1074
Tx public key: 3f9266d79342b0f74ee76cfc5db9a1409cc340f187e5b0dad5f9c4fd082eec81
Timestamp: 1713003154 Timestamp [UCT]: 2024-04-13 10:12:34 Age [y:d:h:m:s]: 00:317:07:21:08
Block: 999533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226833 RingCT/type: yes/0
Extra: 013f9266d79342b0f74ee76cfc5db9a1409cc340f187e5b0dad5f9c4fd082eec8102110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddcc41ab6c4a5f13ac604b7d6d423296581f75ce0fdb1967e463a696e4ccb9a6 0.600000000000 1460013 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": 999543, "vin": [ { "gen": { "height": 999533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddcc41ab6c4a5f13ac604b7d6d423296581f75ce0fdb1967e463a696e4ccb9a6" } } ], "extra": [ 1, 63, 146, 102, 215, 147, 66, 176, 247, 78, 231, 108, 252, 93, 185, 161, 64, 156, 195, 64, 241, 135, 229, 176, 218, 213, 249, 196, 253, 8, 46, 236, 129, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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