Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e720ec0da70d743c9185e23d3f1427924eb185bef13290d63d190d8ad9e663e

Tx prefix hash: ab4e0b667c2bdb91974aca96e615e7379017dcbdb9241d22a04965f4efd264a4
Tx public key: f50ff2e97e968d40894ac47b033433d229fbce97d5aedb258914ee147fe9d4f8
Timestamp: 1581445953 Timestamp [UCT]: 2020-02-11 18:32:33 Age [y:d:h:m:s]: 04:364:11:53:39
Block: 62942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152377 RingCT/type: yes/0
Extra: 01f50ff2e97e968d40894ac47b033433d229fbce97d5aedb258914ee147fe9d4f8021100000002d81c26c0000000000000000000

1 output(s) for total of 379.706332034000 dcy

stealth address amount amount idx
00: 830abbb25aefa7a723b12fd1cc5bde9d5914798809cd460d522d5155cd1842e4 379.706332034000 116065 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": 62952, "vin": [ { "gen": { "height": 62942 } } ], "vout": [ { "amount": 379706332034, "target": { "key": "830abbb25aefa7a723b12fd1cc5bde9d5914798809cd460d522d5155cd1842e4" } } ], "extra": [ 1, 245, 15, 242, 233, 126, 150, 141, 64, 137, 74, 196, 123, 3, 52, 51, 210, 41, 251, 206, 151, 213, 174, 219, 37, 137, 20, 238, 20, 127, 233, 212, 248, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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