Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5d80863ab548fd3f7a3629a0670fe361b0703d06e347fdcc23b2a1c29668cfa

Tx prefix hash: 0b65ee850e28b34ba5f9b3652a0e71a0b7057ca5f59b3f850d3f16e0d6cbf4ab
Tx public key: 0706268856459134d4571fea2ced12c13812b2dcf51311cac40909407bc300c3
Timestamp: 1581822886 Timestamp [UTC]: 2020-02-16 03:14:46 Age [y:d:h:m:s]: 06:017:23:54:59
Block: 65840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1424383 RingCT/type: yes/0
Extra: 010706268856459134d4571fea2ced12c13812b2dcf51311cac40909407bc300c3021100000005026b59f3000000000000000000

1 output(s) for total of 0.371403129020 xmr

stealth address amount amount idx tag
00: c796abfe6f245217b929a0265f76537f6e31290c0980e10d2162c70d5ec012ce 0.371403129020 121453 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 dinastycoin-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": 65850, "vin": [ { "gen": { "height": 65840 } } ], "vout": [ { "amount": 371403129020, "target": { "key": "c796abfe6f245217b929a0265f76537f6e31290c0980e10d2162c70d5ec012ce" } } ], "extra": [ 1, 7, 6, 38, 136, 86, 69, 145, 52, 212, 87, 31, 234, 44, 237, 18, 193, 56, 18, 178, 220, 245, 19, 17, 202, 196, 9, 9, 64, 123, 195, 0, 195, 2, 17, 0, 0, 0, 5, 2, 107, 89, 243, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369