Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 842aef3007f7664e04e20f5046a4bae37ea4e14da82c0649dcbbfa5620f757df

Tx prefix hash: 2f7ba47bd676c9258426b0f887665b7765a246d9461b8843a3105431dd7cba79
Tx public key: 21f2ccaec8683cf831441e4ed29abf981e304ab2f8ca74e9a43c7313ff6cd405
Timestamp: 1771116785 Timestamp [UTC]: 2026-02-15 00:53:05 Age [y:d:h:m:s]: 00:180:12:41:18
Block: 1477991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135153 RingCT/type: yes/0
Extra: 0121f2ccaec8683cf831441e4ed29abf981e304ab2f8ca74e9a43c7313ff6cd405021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c6b106907dd89c90bd9f263f34c181ccb3a67b7e2bc42580609d8f7d32260aa2 0.000600000000 1967311 of 15 -

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": 1478001, "vin": [ { "gen": { "height": 1477991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6b106907dd89c90bd9f263f34c181ccb3a67b7e2bc42580609d8f7d32260aa2" } } ], "extra": [ 1, 33, 242, 204, 174, 200, 104, 60, 248, 49, 68, 30, 78, 210, 154, 191, 152, 30, 48, 74, 178, 248, 202, 116, 233, 164, 60, 115, 19, 255, 108, 212, 5, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: