Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26c67bdacbb903684fcf6be81a949ce3f82603161c73588693509616db8db0e9

Tx prefix hash: c7f02001e9f092d9f571670298168cfcaff4d9c40a8c7f0ee790544b38b85516
Tx public key: 0f3431a0e5512b14114ec8e1a57b278111293a582091a2eea4d399a5471cec6a
Timestamp: 1645779856 Timestamp [UCT]: 2022-02-25 09:04:16 Age [y:d:h:m:s]: 02:316:21:43:12
Block: 446097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745906 RingCT/type: yes/0
Extra: 010f3431a0e5512b14114ec8e1a57b278111293a582091a2eea4d399a5471cec6a021100000006a272b9cb000000000000000000

1 output(s) for total of 20.412478477000 dcy

stealth address amount amount idx
00: 39b0ec11ec3c7e7444187562811b77e6e01dcdb48bab3597ea74959d3f919b11 20.412478477000 859884 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": 446107, "vin": [ { "gen": { "height": 446097 } } ], "vout": [ { "amount": 20412478477, "target": { "key": "39b0ec11ec3c7e7444187562811b77e6e01dcdb48bab3597ea74959d3f919b11" } } ], "extra": [ 1, 15, 52, 49, 160, 229, 81, 43, 20, 17, 78, 200, 225, 165, 123, 39, 129, 17, 41, 58, 88, 32, 145, 162, 238, 164, 211, 153, 165, 71, 28, 236, 106, 2, 17, 0, 0, 0, 6, 162, 114, 185, 203, 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