Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cac0d4e32d97842c5b3a7bad894137e7dc03b21d4cf5af706b901438d7a0b364

Tx prefix hash: 479e55fbb6fe950ce927ee8e8adf2410345c9053c9bf376015aeb12f6cd344b2
Tx public key: 3d7d3fe5c38a9babd4d4d2f1b8f3c47295089771685345132b8fe50a9af5b63e
Timestamp: 1656190742 Timestamp [UTC]: 2022-06-25 20:59:02 Age [y:d:h:m:s]: 03:314:10:06:21
Block: 530296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 996911 RingCT/type: yes/0
Extra: 013d7d3fe5c38a9babd4d4d2f1b8f3c47295089771685345132b8fe50a9af5b63e021100000002cb8520c2000000000000000000

1 output(s) for total of 0.010737653289 xmr

stealth address amount amount idx tag
00: 1ae3e987f597e10b8f87dbfba7f67c883fba15f4e529ad0cdcd1d4f64e030640 0.010737653289 959339 of 0 -

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": 530306, "vin": [ { "gen": { "height": 530296 } } ], "vout": [ { "amount": 10737653289, "target": { "key": "1ae3e987f597e10b8f87dbfba7f67c883fba15f4e529ad0cdcd1d4f64e030640" } } ], "extra": [ 1, 61, 125, 63, 229, 195, 138, 155, 171, 212, 212, 210, 241, 184, 243, 196, 114, 149, 8, 151, 113, 104, 83, 69, 19, 43, 143, 229, 10, 154, 245, 182, 62, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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: