Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fe0a00d0f6559c5b000367230eab21e8f7b4930c918626695df124cdf38be07

Tx prefix hash: 0a3e0b12d22e52720138c46930f77dcc5cac85cc6dcbfbb107fc68291a2ec7e5
Tx public key: dfe3aad11da419827c7372ece3359881d7a391a2492777e394ae4d319f97aa4a
Timestamp: 1682887835 Timestamp [UCT]: 2023-04-30 20:50:35 Age [y:d:h:m:s]: 01:171:16:29:50
Block: 750132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384178 RingCT/type: yes/0
Extra: 01dfe3aad11da419827c7372ece3359881d7a391a2492777e394ae4d319f97aa4a02110000000175e3f0e9000000000000000000

1 output(s) for total of 2.006787986000 dcy

stealth address amount amount idx
00: dce5e04b4b0b29330ea170e8bbd731345d4c8f3a250a7a8d7ccc22167bf913f5 2.006787986000 1198177 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": 750142, "vin": [ { "gen": { "height": 750132 } } ], "vout": [ { "amount": 2006787986, "target": { "key": "dce5e04b4b0b29330ea170e8bbd731345d4c8f3a250a7a8d7ccc22167bf913f5" } } ], "extra": [ 1, 223, 227, 170, 209, 29, 164, 25, 130, 124, 115, 114, 236, 227, 53, 152, 129, 215, 163, 145, 162, 73, 39, 119, 227, 148, 174, 77, 49, 159, 151, 170, 74, 2, 17, 0, 0, 0, 1, 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