Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 128edbab856b3a4dcdbddad7c60b6e631794fb2fd552783e959e273019f01552

Tx prefix hash: 1249848e16d9479ff4e3b604f98dc2e5d41f8a3ad473edba9f39be9f92b82ac8
Tx public key: 6ac514718499260f8bcd83ff4abb4c5103c3930d0e1bb8eca542e235035ca019
Timestamp: 1772013410 Timestamp [UTC]: 2026-02-25 09:56:50 Age [y:d:h:m:s]: 00:267:23:40:32
Block: 1485447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197142 RingCT/type: yes/0
Extra: 016ac514718499260f8bcd83ff4abb4c5103c3930d0e1bb8eca542e235035ca01902110000000ff188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aac868e829160b0c4ee1fa928905ec177dab5a1630d7f0b1f72c79df47103d2b 0.000600000000 1974883 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": 1485457, "vin": [ { "gen": { "height": 1485447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aac868e829160b0c4ee1fa928905ec177dab5a1630d7f0b1f72c79df47103d2b" } } ], "extra": [ 1, 106, 197, 20, 113, 132, 153, 38, 15, 139, 205, 131, 255, 74, 187, 76, 81, 3, 195, 147, 13, 14, 27, 184, 236, 165, 66, 226, 53, 3, 92, 160, 25, 2, 17, 0, 0, 0, 15, 241, 136, 200, 168, 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: