Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99558734ab73c7a521cd661bd3c9f4328b663101cb1f38b9b01d57318e54a72a

Tx prefix hash: 2dddb0f63fcb03e59b9c1162417bdcf4a4c234f1dd9a4c557da8d012cc2f9d2b
Tx public key: 487270425db1cb86e0475da1dae6957b6a0bae85dc5ef057898958f299b2a19f
Timestamp: 1704166565 Timestamp [UCT]: 2024-01-02 03:36:05 Age [y:d:h:m:s]: 01:017:23:43:44
Block: 926279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274159 RingCT/type: yes/0
Extra: 01487270425db1cb86e0475da1dae6957b6a0bae85dc5ef057898958f299b2a19f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f8466403e61f05b87135eb3d113a111aca01c10aaaa7b24d301f54d1afe7267 0.600000000000 1384057 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": 926289, "vin": [ { "gen": { "height": 926279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f8466403e61f05b87135eb3d113a111aca01c10aaaa7b24d301f54d1afe7267" } } ], "extra": [ 1, 72, 114, 112, 66, 93, 177, 203, 134, 224, 71, 93, 161, 218, 230, 149, 123, 106, 11, 174, 133, 220, 94, 240, 87, 137, 137, 88, 242, 153, 178, 161, 159, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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