Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fca6d9e9900afe4f57137c25eeb0e63e68f653c53ce69538bb4d84d38b032126

Tx prefix hash: 67197f2c2dce0facd13312c2f08db3f60e310a188314dc43bf6a36b75792c9b6
Tx public key: 97fab1f0cfb9f13cd36cabf54f1a29cfbcea1f02bdb78438b34edacf09097211
Timestamp: 1742298757 Timestamp [UTC]: 2025-03-18 11:52:37 Age [y:d:h:m:s]: 01:248:00:32:47
Block: 1241966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441433 RingCT/type: yes/0
Extra: 0197fab1f0cfb9f13cd36cabf54f1a29cfbcea1f02bdb78438b34edacf090972110211000000061f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 03ba51a6c32e4e086f6557bbceebc025bad81e30f2cf6961d9de616ae7ff4f84 0.000600000000 1728939 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": 1241976, "vin": [ { "gen": { "height": 1241966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03ba51a6c32e4e086f6557bbceebc025bad81e30f2cf6961d9de616ae7ff4f84" } } ], "extra": [ 1, 151, 250, 177, 240, 207, 185, 241, 60, 211, 108, 171, 245, 79, 26, 41, 207, 188, 234, 31, 2, 189, 183, 132, 56, 179, 78, 218, 207, 9, 9, 114, 17, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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: