Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e25fe444861a59bcd0002dcc215e743c7c0021be5980ad2e642c0a9366a075f

Tx prefix hash: 83504d7c8c574f4ba9502a2b574f89f3ebe07ae3ca266f35cb39ce836de46aa5
Tx public key: a492d7f95e78d005174c3850f8c3d28367e28bef9c30b1a728b3a66b50042343
Timestamp: 1769240595 Timestamp [UTC]: 2026-01-24 07:43:15 Age [y:d:h:m:s]: 00:214:07:30:48
Block: 1462458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159044 RingCT/type: yes/0
Extra: 01a492d7f95e78d005174c3850f8c3d28367e28bef9c30b1a728b3a66b5004234302110000000b215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7c6f5d9933c1f658dbddd3adf82a33cec4d266855c4c5ab0978062cdb0b0c4b0 0.000600000000 1951656 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": 1462468, "vin": [ { "gen": { "height": 1462458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c6f5d9933c1f658dbddd3adf82a33cec4d266855c4c5ab0978062cdb0b0c4b0" } } ], "extra": [ 1, 164, 146, 215, 249, 94, 120, 208, 5, 23, 76, 56, 80, 248, 195, 210, 131, 103, 226, 139, 239, 156, 48, 177, 167, 40, 179, 166, 107, 80, 4, 35, 67, 2, 17, 0, 0, 0, 11, 33, 91, 191, 137, 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: