Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80ff9d0bb25f1508128043c4e2a301ec3cb03da3c46e93769a4a1ec5eb504c2b

Tx prefix hash: 414f741c79ff0ee53efabdfde4c79d5a8da119bcd081f6884f8359df50917010
Tx public key: 66cc75a4f754259aeeb51d3a3320c70941cfd7d4cdbe6821e83a92806941b2f9
Timestamp: 1744350125 Timestamp [UTC]: 2025-04-11 05:42:05 Age [y:d:h:m:s]: 01:215:08:17:17
Block: 1258934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417740 RingCT/type: yes/0
Extra: 0166cc75a4f754259aeeb51d3a3320c70941cfd7d4cdbe6821e83a92806941b2f9021100000007dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b1057d2f9ec0f6bb9b64636a80d328421c799fa7963ae6de8b73daa54b051d70 0.000600000000 1746071 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": 1258944, "vin": [ { "gen": { "height": 1258934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1057d2f9ec0f6bb9b64636a80d328421c799fa7963ae6de8b73daa54b051d70" } } ], "extra": [ 1, 102, 204, 117, 164, 247, 84, 37, 154, 238, 181, 29, 58, 51, 32, 199, 9, 65, 207, 215, 212, 205, 190, 104, 33, 232, 58, 146, 128, 105, 65, 178, 249, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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: