Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e54ba8e6a994557752eb9492f85640022bf5d051833e68e9fbc2f9efa99770

Tx prefix hash: fc0b6bbbfdbe2cd2c12c40174617f76c4cc4778ee2e5269ab95fda74af097c80
Tx public key: 0798be6e82c523ea3c855f441134724986d809675b2e9377957f59682abc5708
Timestamp: 1735742510 Timestamp [UTC]: 2025-01-01 14:41:50 Age [y:d:h:m:s]: 01:319:18:29:44
Block: 1187934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492351 RingCT/type: yes/0
Extra: 010798be6e82c523ea3c855f441134724986d809675b2e9377957f59682abc5708021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 24c276908bc2111f7519da0cb48e5b9f9abf738865e9a7dd4dfc57dca9609bf3 0.000600000000 1674433 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": 1187944, "vin": [ { "gen": { "height": 1187934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24c276908bc2111f7519da0cb48e5b9f9abf738865e9a7dd4dfc57dca9609bf3" } } ], "extra": [ 1, 7, 152, 190, 110, 130, 197, 35, 234, 60, 133, 95, 68, 17, 52, 114, 73, 134, 216, 9, 103, 91, 46, 147, 119, 149, 127, 89, 104, 42, 188, 87, 8, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: