Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7538ef8d30a713edd67bafd3487f140c98e82c32b59ef403e6951b4530e9415e

Tx prefix hash: 4c02892546f2d15f4117b6e314f4d37094d9157d4e4378540a79a8e0a9564b83
Tx public key: 98bc28857f9a616bafab472af136b1daa2d991584f58bb70a5bdd47eb9207e28
Timestamp: 1723735369 Timestamp [UCT]: 2024-08-15 15:22:49 Age [y:d:h:m:s]: 00:235:12:50:30
Block: 1088529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168197 RingCT/type: yes/0
Extra: 0198bc28857f9a616bafab472af136b1daa2d991584f58bb70a5bdd47eb9207e28021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d2e57f8110d54588e4e026d5fea21b53d5e401a6baf13711414c3f5a01ec806 0.600000000000 1563146 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": 1088539, "vin": [ { "gen": { "height": 1088529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d2e57f8110d54588e4e026d5fea21b53d5e401a6baf13711414c3f5a01ec806" } } ], "extra": [ 1, 152, 188, 40, 133, 127, 154, 97, 107, 175, 171, 71, 42, 241, 54, 177, 218, 162, 217, 145, 88, 79, 88, 187, 112, 165, 189, 212, 126, 185, 32, 126, 40, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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