Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 050a5f5a1ec0d9fe0c39cd4400f8af7d062a80af72b892e672f0cb85f242dac7

Tx prefix hash: 600a6d01f01b0baff1393b14c5a1c5d85fe6a8efea28cbcbb3219291feecc0f4
Tx public key: df223637f6b0468d59583ec0bb054991c3811b31e4a9117b2f1d1fa0605f5f54
Timestamp: 1750360281 Timestamp [UTC]: 2025-06-19 19:11:21 Age [y:d:h:m:s]: 01:151:05:54:38
Block: 1308561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372210 RingCT/type: yes/0
Extra: 01df223637f6b0468d59583ec0bb054991c3811b31e4a9117b2f1d1fa0605f5f54021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 97d270a834a0b3f61d899d7db88efc211a642186ac7700ad8734baee01fe107e 0.000600000000 1796174 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": 1308571, "vin": [ { "gen": { "height": 1308561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97d270a834a0b3f61d899d7db88efc211a642186ac7700ad8734baee01fe107e" } } ], "extra": [ 1, 223, 34, 54, 55, 246, 176, 70, 141, 89, 88, 62, 192, 187, 5, 73, 145, 195, 129, 27, 49, 228, 169, 17, 123, 47, 29, 31, 160, 96, 95, 95, 84, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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: