Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef762a239d23e0a74ccef8c68d57ba2c566e606f7dc5f6e4f5f68d4dbe0277d7

Tx prefix hash: c908e41e4a5d1600d72c15bb30973aa0c72ce708a69b34134c70f44ac0a5630c
Tx public key: d59584b20bb45405d05eb42e9987abe2e5ab53c4d42e198a6f26a290864d670e
Timestamp: 1647385286 Timestamp [UTC]: 2022-03-15 23:01:26 Age [y:d:h:m:s]: 04:248:23:51:07
Block: 459260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1222191 RingCT/type: yes/0
Extra: 01d59584b20bb45405d05eb42e9987abe2e5ab53c4d42e198a6f26a290864d670e021100000005d3fcec30000000000000000000

1 output(s) for total of 0.018462105880 xmr

stealth address amount amount idx tag
00: f6c0def8fd0cf6f1145b87bbea73e535405fdef64ef1d223a715ecf2589b3208 0.018462105880 875965 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": 459270, "vin": [ { "gen": { "height": 459260 } } ], "vout": [ { "amount": 18462105880, "target": { "key": "f6c0def8fd0cf6f1145b87bbea73e535405fdef64ef1d223a715ecf2589b3208" } } ], "extra": [ 1, 213, 149, 132, 178, 11, 180, 84, 5, 208, 94, 180, 46, 153, 135, 171, 226, 229, 171, 83, 196, 212, 46, 25, 138, 111, 38, 162, 144, 134, 77, 103, 14, 2, 17, 0, 0, 0, 5, 211, 252, 236, 48, 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: