Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f33d5c1f6258513247f72507eb2abd6432af2656fc1728f6dc9d07d52de6e2ac

Tx prefix hash: d32fd0e6db79c89e6af66833e9df5ee92b2663320254959ad1393d57dade2bc0
Tx public key: f65fc884c8def9e99f7eb6f7308cbd921a8c91a7b202a090c3ef04f6c85373d3
Timestamp: 1724457455 Timestamp [UCT]: 2024-08-23 23:57:35 Age [y:d:h:m:s]: 00:220:06:48:10
Block: 1094519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157284 RingCT/type: yes/0
Extra: 01f65fc884c8def9e99f7eb6f7308cbd921a8c91a7b202a090c3ef04f6c85373d302110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54adc0474e0434af599edd135abe8602f06bb6a3d10acf99dd73bda33bb1485b 0.600000000000 1569636 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": 1094529, "vin": [ { "gen": { "height": 1094519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54adc0474e0434af599edd135abe8602f06bb6a3d10acf99dd73bda33bb1485b" } } ], "extra": [ 1, 246, 95, 200, 132, 200, 222, 249, 233, 159, 126, 182, 247, 48, 140, 189, 146, 26, 140, 145, 167, 178, 2, 160, 144, 195, 239, 4, 246, 200, 83, 115, 211, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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