Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 712ffb31aaeec1be444c5ee398b7cbe89ddf36e9dd315eebd3e7d3ebb0e148c7

Tx prefix hash: 338a7af1866ac727ecf9149cac8ab5b907ebd1c8db3f9c6adf333acbd545838e
Tx public key: dab92121f046b11aed6efb25cc56b391f0a39eecdcf78a3fd46c114cfa36bce5
Timestamp: 1770285471 Timestamp [UTC]: 2026-02-05 09:57:51 Age [y:d:h:m:s]: 00:280:10:38:55
Block: 1471148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205742 RingCT/type: yes/0
Extra: 01dab92121f046b11aed6efb25cc56b391f0a39eecdcf78a3fd46c114cfa36bce5021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a4bf1eb3324e56c04177a2a5c2f29a5950a04b11f3c2c6967d1e4a61cf2796e4 0.000600000000 1960418 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": 1471158, "vin": [ { "gen": { "height": 1471148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4bf1eb3324e56c04177a2a5c2f29a5950a04b11f3c2c6967d1e4a61cf2796e4" } } ], "extra": [ 1, 218, 185, 33, 33, 240, 70, 177, 26, 237, 110, 251, 37, 204, 86, 179, 145, 240, 163, 158, 236, 220, 247, 138, 63, 212, 108, 17, 76, 250, 54, 188, 229, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: