Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82f1198cd36ef054ecc0fcf06e4bf574a8d674034b4d470a1eee295a9a3a7b8e

Tx prefix hash: 4c8488607c8007fb9d092b8c2d721994d667f1c3c73060848ae8196ad38bd00c
Tx public key: 6f986d365d5bc4a047549d51a4ee3a8ce5525ef72e02f33b5e4f4cb1e9d62b65
Timestamp: 1713513323 Timestamp [UCT]: 2024-04-19 07:55:23 Age [y:d:h:m:s]: 00:362:20:04:08
Block: 1003773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259393 RingCT/type: yes/0
Extra: 016f986d365d5bc4a047549d51a4ee3a8ce5525ef72e02f33b5e4f4cb1e9d62b6502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0d60ffff1e14750cdb6b602e51c3d72ab3615c6a3de17a103c01b81386f3cc1 0.600000000000 1464317 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": 1003783, "vin": [ { "gen": { "height": 1003773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0d60ffff1e14750cdb6b602e51c3d72ab3615c6a3de17a103c01b81386f3cc1" } } ], "extra": [ 1, 111, 152, 109, 54, 93, 91, 196, 160, 71, 84, 157, 81, 164, 238, 58, 140, 229, 82, 94, 247, 46, 2, 243, 59, 94, 79, 76, 177, 233, 214, 43, 101, 2, 17, 0, 0, 0, 1, 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