Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0256857ed565a7c0edef7175dc47ebe29d6ef9531e6e041381f6e68b34e5dd1

Tx prefix hash: 880fd3f4f899da69cbc4b190e209c222e3d2afb17f4a3e03a500487282d45606
Tx public key: 38712cde6aa1c93be1d68154a509672ab816ebc3c5df67f98efb20f3f13923ca
Timestamp: 1587779627 Timestamp [UTC]: 2020-04-25 01:53:47 Age [y:d:h:m:s]: 06:123:01:35:11
Block: 95470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1524936 RingCT/type: yes/0
Extra: 0138712cde6aa1c93be1d68154a509672ab816ebc3c5df67f98efb20f3f13923ca02110000005537fb5df4000000000000000000

1 output(s) for total of 0.296257276501 xmr

stealth address amount amount idx tag
00: a0d8ea83e7646bd7253bda7fddaa702e7db5b44d364714bf64719ba0f8a825be 0.296257276501 169671 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": 95480, "vin": [ { "gen": { "height": 95470 } } ], "vout": [ { "amount": 296257276501, "target": { "key": "a0d8ea83e7646bd7253bda7fddaa702e7db5b44d364714bf64719ba0f8a825be" } } ], "extra": [ 1, 56, 113, 44, 222, 106, 161, 201, 59, 225, 214, 129, 84, 165, 9, 103, 42, 184, 22, 235, 195, 197, 223, 103, 249, 142, 251, 32, 243, 241, 57, 35, 202, 2, 17, 0, 0, 0, 85, 55, 251, 93, 244, 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: