Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c902e3e1e5f12c2f89f3c64b7a868f9f9d96a8ada14c6073e6f57e3efbb3828

Tx prefix hash: 4a995411b480eefbbecb03fd31bcf65fdbd4ec8f460a31d53f1ff9e83ed4cc6c
Tx public key: 5d3ff0c52fea77f2b4a779be9aee7ac1895d6c07174049b8c045579b84e77cb0
Timestamp: 1588737016 Timestamp [UCT]: 2020-05-06 03:50:16 Age [y:d:h:m:s]: 04:236:10:59:31
Block: 99032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085330 RingCT/type: yes/0
Extra: 015d3ff0c52fea77f2b4a779be9aee7ac1895d6c07174049b8c045579b84e77cb0021100000160a86a1a65000000000000000000

1 output(s) for total of 288.314601293000 dcy

stealth address amount amount idx
00: e3f74237e77e82132c0ff3801ddd53e662168a4a75e95b5b43080f510c675256 288.314601293000 174866 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": 99042, "vin": [ { "gen": { "height": 99032 } } ], "vout": [ { "amount": 288314601293, "target": { "key": "e3f74237e77e82132c0ff3801ddd53e662168a4a75e95b5b43080f510c675256" } } ], "extra": [ 1, 93, 63, 240, 197, 47, 234, 119, 242, 180, 167, 121, 190, 154, 238, 122, 193, 137, 93, 108, 7, 23, 64, 73, 184, 192, 69, 87, 155, 132, 231, 124, 176, 2, 17, 0, 0, 1, 96, 168, 106, 26, 101, 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