Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 298cc8b2b75b578cf3216b964b1bac54457fbd996a362733c622e6f1cfa421c1

Tx prefix hash: 250db48f31b25d695affad2d8851cb8cf763c17fcfacd270e02433eb1e6e9cb6
Tx public key: 5f51651c8e5543f9d33bb2cebfb336158357f979ad5e229f5799b31640924b4d
Timestamp: 1710618098 Timestamp [UCT]: 2024-03-16 19:41:38 Age [y:d:h:m:s]: 00:243:04:29:56
Block: 979794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174095 RingCT/type: yes/0
Extra: 015f51651c8e5543f9d33bb2cebfb336158357f979ad5e229f5799b31640924b4d02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b64ac1c0ba3a8ca8e6f2f688c4bb88bccf1595e539e1f71f4a913d0c47053662 0.600000000000 1439849 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": 979804, "vin": [ { "gen": { "height": 979794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b64ac1c0ba3a8ca8e6f2f688c4bb88bccf1595e539e1f71f4a913d0c47053662" } } ], "extra": [ 1, 95, 81, 101, 28, 142, 85, 67, 249, 211, 59, 178, 206, 191, 179, 54, 21, 131, 87, 249, 121, 173, 94, 34, 159, 87, 153, 179, 22, 64, 146, 75, 77, 2, 17, 0, 0, 0, 12, 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