Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1aa09003cb969b72a2cb6da8adaf1fa578ec52255f910b09691a70ebdd010a6a

Tx prefix hash: f39d4c286cf7c20891b2d80d8b231a0b13e67c1253d6f5ffbf885238fe5d271b
Tx public key: 35211fcfd5b200c894a0cddd83e98b08bcb116e9d931cb1f27ce5d12ab901337
Timestamp: 1756341494 Timestamp [UTC]: 2025-08-28 00:38:14 Age [y:d:h:m:s]: 00:256:00:08:29
Block: 1355926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175603 RingCT/type: yes/0
Extra: 0135211fcfd5b200c894a0cddd83e98b08bcb116e9d931cb1f27ce5d12ab90133702110000000dad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 122554adfff71659d40eed6647987bc24ab8e2932147f2949c398fa005ff8fe8 0.000600000000 1843929 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": 1355936, "vin": [ { "gen": { "height": 1355926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "122554adfff71659d40eed6647987bc24ab8e2932147f2949c398fa005ff8fe8" } } ], "extra": [ 1, 53, 33, 31, 207, 213, 178, 0, 200, 148, 160, 205, 221, 131, 233, 139, 8, 188, 177, 22, 233, 217, 49, 203, 31, 39, 206, 93, 18, 171, 144, 19, 55, 2, 17, 0, 0, 0, 13, 173, 121, 72, 208, 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: