Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c226b8ac97cb6a997d207497d3f45af41cad587f43bdcd4095ce3f5adb4946e1

Tx prefix hash: cf75840f96c550c50fd4488e756447f0f75f28b250c321c9e2b38d47aeffa961
Tx public key: edf91ab6d9506793140b19ada2b869f7474a1b41cbe8d6c5bef72d4dbe821905
Timestamp: 1575842004 Timestamp [UTC]: 2019-12-08 21:53:24 Age [y:d:h:m:s]: 06:288:11:12:19
Block: 23398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1616855 RingCT/type: yes/0
Extra: 01edf91ab6d9506793140b19ada2b869f7474a1b41cbe8d6c5bef72d4dbe8219050211000000149159db1e000000000000000000

1 output(s) for total of 0.513447498844 xmr

stealth address amount amount idx tag
00: e2d9c1180768c9d1e312803a9e7ea91b0e1be1e8af5031fb76e9b84eb06588a0 0.513447498844 37577 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": 23408, "vin": [ { "gen": { "height": 23398 } } ], "vout": [ { "amount": 513447498844, "target": { "key": "e2d9c1180768c9d1e312803a9e7ea91b0e1be1e8af5031fb76e9b84eb06588a0" } } ], "extra": [ 1, 237, 249, 26, 182, 217, 80, 103, 147, 20, 11, 25, 173, 162, 184, 105, 247, 71, 74, 27, 65, 203, 232, 214, 197, 190, 247, 45, 77, 190, 130, 25, 5, 2, 17, 0, 0, 0, 20, 145, 89, 219, 30, 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: