Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4235091e9fae251e71781749e4a03231a5ecc2ce31fc2cca1da8a8e023d5358c

Tx prefix hash: 8ed9bb202b948088d8f0c1e5498b249e2be63c0813109e831c4fa6475388c5b6
Tx public key: 0ad1c8163375fc0aef06219e5fc10cb765c953689ad8733ef1efed50518ec25b
Timestamp: 1577792707 Timestamp [UTC]: 2019-12-31 11:45:07 Age [y:d:h:m:s]: 06:327:08:46:44
Block: 35689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1647805 RingCT/type: yes/0
Extra: 010ad1c8163375fc0aef06219e5fc10cb765c953689ad8733ef1efed50518ec25b0211000000034ac5aa02000000000000000000

1 output(s) for total of 0.467464226919 xmr

stealth address amount amount idx tag
00: cf86e06af77728cc06da93d86a3fc05ee30e834534b80576f16104ed4176a142 0.467464226919 60262 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": 35699, "vin": [ { "gen": { "height": 35689 } } ], "vout": [ { "amount": 467464226919, "target": { "key": "cf86e06af77728cc06da93d86a3fc05ee30e834534b80576f16104ed4176a142" } } ], "extra": [ 1, 10, 209, 200, 22, 51, 117, 252, 10, 239, 6, 33, 158, 95, 193, 12, 183, 101, 201, 83, 104, 154, 216, 115, 62, 241, 239, 237, 80, 81, 142, 194, 91, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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: