Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a745db2fef4195f46b2f08812f23730f2f349c274545a7e9ce92e461ec44f65

Tx prefix hash: a8a04e12f0c036e70314aa2f0a33ad1ff8a1b71979cdfd07f6578d44b48f3a62
Tx public key: 7c8f5a9792143c5c2e7f0347e12c435370a8c87cff6800b85acec7248df76ea1
Timestamp: 1741764940 Timestamp [UTC]: 2025-03-12 07:35:40 Age [y:d:h:m:s]: 01:059:13:21:37
Block: 1237539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293801 RingCT/type: yes/0
Extra: 017c8f5a9792143c5c2e7f0347e12c435370a8c87cff6800b85acec7248df76ea10211000000071f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2e7b81f04a2699c1989d6f7d76f24af1eb1a26c83aca10b4d5f680241c570047 0.000600000000 1724494 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": 1237549, "vin": [ { "gen": { "height": 1237539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e7b81f04a2699c1989d6f7d76f24af1eb1a26c83aca10b4d5f680241c570047" } } ], "extra": [ 1, 124, 143, 90, 151, 146, 20, 60, 92, 46, 127, 3, 71, 225, 44, 67, 83, 112, 168, 200, 124, 255, 104, 0, 184, 90, 206, 199, 36, 141, 247, 110, 161, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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: