Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e801e6f6e43ba05ca70f155d880a953b3ff26e99404a4da18dde0427794fdb5

Tx prefix hash: d54b2b8c4367575da5968ae71a274e33e7c84d0dcac7d0ff5974a381159d4ec2
Tx public key: e482b7dfd1767e21ebf839f873b0c97c30e72019b67f03b3e8c23c53735e50e8
Timestamp: 1593622880 Timestamp [UCT]: 2020-07-01 17:01:20 Age [y:d:h:m:s]: 04:314:23:41:53
Block: 112538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168180 RingCT/type: yes/0
Extra: 01e482b7dfd1767e21ebf839f873b0c97c30e72019b67f03b3e8c23c53735e50e802110000000a8a2ee0d9000000000000000000

1 output(s) for total of 260.089696381000 dcy

stealth address amount amount idx
00: ff3923bb484de51a79a68681c14cd0b0caf628c655030923d73a370d46e6a8a5 260.089696381000 194081 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": 112548, "vin": [ { "gen": { "height": 112538 } } ], "vout": [ { "amount": 260089696381, "target": { "key": "ff3923bb484de51a79a68681c14cd0b0caf628c655030923d73a370d46e6a8a5" } } ], "extra": [ 1, 228, 130, 183, 223, 209, 118, 126, 33, 235, 248, 57, 248, 115, 176, 201, 124, 48, 231, 32, 25, 182, 127, 3, 179, 232, 194, 60, 83, 115, 94, 80, 232, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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