Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7699611a09833fbc6bd86e1b14f79026bc5442b66536095b833f2990559c1b6

Tx prefix hash: ff22e8fa83c6a2ddc9fa91df99aaf7f9b713f8a8cbd08b4a3928650d10d8b4e9
Tx public key: e20078552f20a7159c3b9e9235810b2a98609518f22c9c5c6dbe55cc1f2264c1
Timestamp: 1581993691 Timestamp [UCT]: 2020-02-18 02:41:31 Age [y:d:h:m:s]: 04:357:20:06:21
Block: 67153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147943 RingCT/type: yes/0
Extra: 01e20078552f20a7159c3b9e9235810b2a98609518f22c9c5c6dbe55cc1f2264c1021100000001724f989b000000000000000000

1 output(s) for total of 367.701195864000 dcy

stealth address amount amount idx
00: a9b413ce3f2309e4d6d0fff964cd539231439f5e42cec29473c8d5dc005b0426 367.701195864000 123714 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": 67163, "vin": [ { "gen": { "height": 67153 } } ], "vout": [ { "amount": 367701195864, "target": { "key": "a9b413ce3f2309e4d6d0fff964cd539231439f5e42cec29473c8d5dc005b0426" } } ], "extra": [ 1, 226, 0, 120, 85, 47, 32, 167, 21, 156, 59, 158, 146, 53, 129, 11, 42, 152, 96, 149, 24, 242, 44, 156, 92, 109, 190, 85, 204, 31, 34, 100, 193, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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