Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f240f23224e1564b294968d0c4dc56649138e6cc0dab0a82a764626d0353e6f3

Tx prefix hash: 5d4d3fd6e039d4cf0bd9809afafc7795850811eeb72ad093b14e1dcc08bde342
Tx public key: a127be381b1963888b0fb83deddcecca6d918d6cbf8bf2787941594f73eb9c7f
Timestamp: 1583816478 Timestamp [UCT]: 2020-03-10 05:01:18 Age [y:d:h:m:s]: 04:293:03:36:14
Block: 79583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104593 RingCT/type: yes/0
Extra: 01a127be381b1963888b0fb83deddcecca6d918d6cbf8bf2787941594f73eb9c7f0211000000174943cd9f000000000000000000

1 output(s) for total of 334.444675834000 dcy

stealth address amount amount idx
00: 44d89048204891f931614e624636d3a5c30dc5e0928fb7d6a08394952bc1e7b3 334.444675834000 145633 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": 79593, "vin": [ { "gen": { "height": 79583 } } ], "vout": [ { "amount": 334444675834, "target": { "key": "44d89048204891f931614e624636d3a5c30dc5e0928fb7d6a08394952bc1e7b3" } } ], "extra": [ 1, 161, 39, 190, 56, 27, 25, 99, 136, 139, 15, 184, 61, 237, 220, 236, 202, 109, 145, 141, 108, 191, 139, 242, 120, 121, 65, 89, 79, 115, 235, 156, 127, 2, 17, 0, 0, 0, 23, 73, 67, 205, 159, 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