Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c5fd3529cfa362d835a0c2596dfbac92cb70bb0fbe2ab8a2c2df14133c7de54

Tx prefix hash: 21def71e413bc1c9112d9a5f319e7faf0176bbf74a302a4ea8b3f829a2673d58
Tx public key: 8047f95004b87da291c39960e68f3265f805d1253d47b1a716bcfb8fafc5019a
Timestamp: 1575077885 Timestamp [UTC]: 2019-11-30 01:38:05 Age [y:d:h:m:s]: 06:081:17:15:30
Block: 20324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1459625 RingCT/type: yes/0
Extra: 018047f95004b87da291c39960e68f3265f805d1253d47b1a716bcfb8fafc5019a020d39303031000300000004ffd263

1 output(s) for total of 0.525604442696 xmr

stealth address amount amount idx tag
00: 808c96ba61495f3cce5e0d3f1aa1f936c2219eb7d534866f16d90c36dba0a1b5 0.525604442696 32470 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": 20334, "vin": [ { "gen": { "height": 20324 } } ], "vout": [ { "amount": 525604442696, "target": { "key": "808c96ba61495f3cce5e0d3f1aa1f936c2219eb7d534866f16d90c36dba0a1b5" } } ], "extra": [ 1, 128, 71, 249, 80, 4, 184, 125, 162, 145, 195, 153, 96, 230, 143, 50, 101, 248, 5, 209, 37, 61, 71, 177, 167, 22, 188, 251, 143, 175, 197, 1, 154, 2, 13, 57, 48, 48, 49, 0, 3, 0, 0, 0, 4, 255, 210, 99 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369