Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4fe6b22f16ea9afb11ecb319f641ead650bc33c4e71e96178299c240dee030f

Tx prefix hash: 4b7734e1ffa57013296effc099c9e25136d69ba1f80eeaca308b2750b3c732ca
Tx public key: a6153bd771abccaa7e35d53de58048cde5bbed4cee1a5fe201f08b61e5f805e2
Timestamp: 1615854576 Timestamp [UCT]: 2021-03-16 00:29:36 Age [y:d:h:m:s]: 04:061:21:32:09
Block: 219397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1064334 RingCT/type: yes/0
Extra: 01a6153bd771abccaa7e35d53de58048cde5bbed4cee1a5fe201f08b61e5f805e202110000008990ec05ad000000000000000000

1 output(s) for total of 115.092562555000 dcy

stealth address amount amount idx
00: c4682f391687bf7c3c2d2a82b883357c8b6fd8bd06e2075c59cc2b38040ae1ea 115.092562555000 451267 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 dinasty-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": 219407, "vin": [ { "gen": { "height": 219397 } } ], "vout": [ { "amount": 115092562555, "target": { "key": "c4682f391687bf7c3c2d2a82b883357c8b6fd8bd06e2075c59cc2b38040ae1ea" } } ], "extra": [ 1, 166, 21, 59, 215, 113, 171, 204, 170, 126, 53, 213, 61, 229, 128, 72, 205, 229, 187, 237, 76, 238, 26, 95, 226, 1, 240, 139, 97, 229, 248, 5, 226, 2, 17, 0, 0, 0, 137, 144, 236, 5, 173, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8