Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 500a691a632424cfbf269c44fdad5b2d0cb61a42dde8a6fc8d3d91285ca44e86

Tx prefix hash: ffb46cb82b841887f69b999bcc3dab6ca77abc49e60dbc4ae8deb79ec8f40c7b
Tx public key: 6928ef50bc9c5f6013e2d6e5f6d4c2bcf3d552e5ffa2204552222538b807c79b
Timestamp: 1715400719 Timestamp [UCT]: 2024-05-11 04:11:59 Age [y:d:h:m:s]: 00:260:18:57:42
Block: 1019450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186461 RingCT/type: yes/0
Extra: 016928ef50bc9c5f6013e2d6e5f6d4c2bcf3d552e5ffa2204552222538b807c79b02110000000b679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2fa7ca6f25835285bf554847c0e4c652fef5aabd0f920223411723ccbc1209e 0.600000000000 1483419 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": 1019460, "vin": [ { "gen": { "height": 1019450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2fa7ca6f25835285bf554847c0e4c652fef5aabd0f920223411723ccbc1209e" } } ], "extra": [ 1, 105, 40, 239, 80, 188, 156, 95, 96, 19, 226, 214, 229, 246, 212, 194, 188, 243, 213, 82, 229, 255, 162, 32, 69, 82, 34, 37, 56, 184, 7, 199, 155, 2, 17, 0, 0, 0, 11, 103, 154, 138, 129, 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