Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8fe7076f003ff02578454ca3af220dc02c42785a9fe256ff80076b06e79f918

Tx prefix hash: 00ab7810d7ad883e3980c5c71af230c7e0a3cb5bacc354ad7d61d1d713db0e19
Tx public key: 259ce2500792512a8cf9c19594ec4ab8644e8102f141a2a5153b382d8d5a46bb
Timestamp: 1731885519 Timestamp [UTC]: 2024-11-17 23:18:39 Age [y:d:h:m:s]: 02:001:01:47:41
Block: 1156004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525521 RingCT/type: yes/0
Extra: 01259ce2500792512a8cf9c19594ec4ab8644e8102f141a2a5153b382d8d5a46bb021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dcacf5a4cf37ceb24ee56c5617d00e4b991d132387b975622872a458db2c59f4 0.000600000000 1641623 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": 1156014, "vin": [ { "gen": { "height": 1156004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcacf5a4cf37ceb24ee56c5617d00e4b991d132387b975622872a458db2c59f4" } } ], "extra": [ 1, 37, 156, 226, 80, 7, 146, 81, 42, 140, 249, 193, 149, 148, 236, 74, 184, 100, 78, 129, 2, 241, 65, 162, 165, 21, 59, 56, 45, 141, 90, 70, 187, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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: