Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557bf9fdb6f6c07f27e66e8d987b3b3db1594d13e40cccb88ef3c3368164d6f6

Tx prefix hash: abf1eeb151f8effb67365c52b9382ec697f56514d4273e645830be4beae47d99
Tx public key: dd9587d447db851f92485521ef63aef5c1edf762600463d17900e2ff39ec1fb0
Timestamp: 1579798266 Timestamp [UTC]: 2020-01-23 16:51:06 Age [y:d:h:m:s]: 06:114:20:04:59
Block: 51546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1483554 RingCT/type: yes/0
Extra: 01dd9587d447db851f92485521ef63aef5c1edf762600463d17900e2ff39ec1fb00211000000012264afe6000000000000000000

1 output(s) for total of 0.414197558835 xmr

stealth address amount amount idx tag
00: 05453ca60ce6945d04f55da12f41f5d12e7e427e8cc95f3e5992813634679795 0.414197558835 95583 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": 51556, "vin": [ { "gen": { "height": 51546 } } ], "vout": [ { "amount": 414197558835, "target": { "key": "05453ca60ce6945d04f55da12f41f5d12e7e427e8cc95f3e5992813634679795" } } ], "extra": [ 1, 221, 149, 135, 212, 71, 219, 133, 31, 146, 72, 85, 33, 239, 99, 174, 245, 193, 237, 247, 98, 96, 4, 99, 209, 121, 0, 226, 255, 57, 236, 31, 176, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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) | monero version: