Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47f9de1fe7916a3d3e9eeaaad4acf95ab7a9e1eaf02904c9ac37fa8f18e2dd0f

Tx prefix hash: 0ac03e2a54952309dfdf03042bd4d8ad563c84dd21c8db694e7eae040503ed5d
Tx public key: 9e9e7a811f039c42204f05f57b571b813be35ed9fe0584572c4222c1f3bfb5ca
Timestamp: 1745971519 Timestamp [UTC]: 2025-04-30 00:05:19 Age [y:d:h:m:s]: 01:009:20:20:28
Block: 1272356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258244 RingCT/type: yes/0
Extra: 019e9e7a811f039c42204f05f57b571b813be35ed9fe0584572c4222c1f3bfb5ca0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e37c1d81a2299382a49f3b56171bb4bcfc69c4d56bd5d8a9212b6830f503b76b 0.000600000000 1759631 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": 1272366, "vin": [ { "gen": { "height": 1272356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e37c1d81a2299382a49f3b56171bb4bcfc69c4d56bd5d8a9212b6830f503b76b" } } ], "extra": [ 1, 158, 158, 122, 129, 31, 3, 156, 66, 32, 79, 5, 245, 123, 87, 27, 129, 59, 227, 94, 217, 254, 5, 132, 87, 44, 66, 34, 193, 243, 191, 181, 202, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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: