Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee350c71c0bf12188d1ff2a8324c32bce17026ec474602df8fbc33100392f879

Tx prefix hash: 5a259ca33435c4ba42f1b9ce1f56386675034d99444ee8cd4ff465ba8de6604a
Tx public key: be0aa6bf1290d7242ed8963d5d440ef22b0d27e8ce50ebfb2736d6c671e0a664
Timestamp: 1722232048 Timestamp [UTC]: 2024-07-29 05:47:28 Age [y:d:h:m:s]: 02:055:07:34:22
Block: 1076061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565031 RingCT/type: yes/0
Extra: 01be0aa6bf1290d7242ed8963d5d440ef22b0d27e8ce50ebfb2736d6c671e0a66402110000000891e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3a1373869f21665309989743da95cf5f5fafa6ff5523df6d939ac2bf76bd2c49 0.000600000000 1548596 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": 1076071, "vin": [ { "gen": { "height": 1076061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a1373869f21665309989743da95cf5f5fafa6ff5523df6d939ac2bf76bd2c49" } } ], "extra": [ 1, 190, 10, 166, 191, 18, 144, 215, 36, 46, 216, 150, 61, 93, 68, 14, 242, 43, 13, 39, 232, 206, 80, 235, 251, 39, 54, 214, 198, 113, 224, 166, 100, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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: