Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1db19b9fd7d78995d1556c23c1aed504d4bcbcc0d699a3480cf8f9cdf38bcfd0

Tx prefix hash: 4d935c06621c9530718ed7896db04b1a3c6eeff5d525b3adb7bf87108ce150c0
Tx public key: 3be3c74947dfc4622f5dc8cabcfcb34a74f9d3d1e966e8c48ed34aa0384f88c5
Timestamp: 1700740287 Timestamp [UCT]: 2023-11-23 11:51:27 Age [y:d:h:m:s]: 01:124:01:12:25
Block: 897885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349807 RingCT/type: yes/0
Extra: 013be3c74947dfc4622f5dc8cabcfcb34a74f9d3d1e966e8c48ed34aa0384f88c502110000000975e3f0e9000000000000000000

1 output(s) for total of 0.650031274000 dcy

stealth address amount amount idx
00: 67d9a71ee4c29342bfc651d54bd054566492ab1454d53b6bd26c6a96aab5d875 0.650031274000 1354282 of 0

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": 897895, "vin": [ { "gen": { "height": 897885 } } ], "vout": [ { "amount": 650031274, "target": { "key": "67d9a71ee4c29342bfc651d54bd054566492ab1454d53b6bd26c6a96aab5d875" } } ], "extra": [ 1, 59, 227, 199, 73, 71, 223, 196, 98, 47, 93, 200, 202, 188, 252, 179, 74, 116, 249, 211, 209, 233, 102, 232, 196, 142, 211, 74, 160, 56, 79, 136, 197, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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