Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2b8e60f0112ea3e023f4e904cf949afae19b4cd1bac9eab4d98e80c57cf361d

Tx prefix hash: c1c384f89f230d7c2232ccb1a12f9846c583ad34d51eba9281853d086daf0db9
Tx public key: f56a7f93295f865ff62c29a4211cbd9c77573673e4d40a85029fe6cfa2f0bd0a
Timestamp: 1699696037 Timestamp [UCT]: 2023-11-11 09:47:17 Age [y:d:h:m:s]: 01:073:03:17:15
Block: 889233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313640 RingCT/type: yes/0
Extra: 01f56a7f93295f865ff62c29a4211cbd9c77573673e4d40a85029fe6cfa2f0bd0a021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.694387560000 dcy

stealth address amount amount idx
00: cc32618a2bc2d3b05aa2f2b2c2e3793fe6da12b384f6363253dbc20b7a4185c1 0.694387560000 1345214 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": 889243, "vin": [ { "gen": { "height": 889233 } } ], "vout": [ { "amount": 694387560, "target": { "key": "cc32618a2bc2d3b05aa2f2b2c2e3793fe6da12b384f6363253dbc20b7a4185c1" } } ], "extra": [ 1, 245, 106, 127, 147, 41, 95, 134, 95, 246, 44, 41, 164, 33, 28, 189, 156, 119, 87, 54, 115, 228, 212, 10, 133, 2, 159, 230, 207, 162, 240, 189, 10, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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