Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75d7c36e02eacc17698b339dc7813ffa88c64b756f8154c0a1a17b6e8d5a5471

Tx prefix hash: 6b16008be85d4e45f9d5b7e55c89e719d8b7a73db36d9e7c1aa2adb3863236cc
Tx public key: c8610e06000872e8965e957069b092867ef89f0dc48b89a42b24ee310ee044ac
Timestamp: 1704867563 Timestamp [UCT]: 2024-01-10 06:19:23 Age [y:d:h:m:s]: 01:313:16:55:14
Block: 932084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483043 RingCT/type: yes/0
Extra: 01c8610e06000872e8965e957069b092867ef89f0dc48b89a42b24ee310ee044ac02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87b5cb3ab0fcacf138f4ed8222bad0c947dcb02d8431ea59f24be85d975bd9b9 0.600000000000 1390004 of 15

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": 932094, "vin": [ { "gen": { "height": 932084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87b5cb3ab0fcacf138f4ed8222bad0c947dcb02d8431ea59f24be85d975bd9b9" } } ], "extra": [ 1, 200, 97, 14, 6, 0, 8, 114, 232, 150, 94, 149, 112, 105, 176, 146, 134, 126, 248, 159, 13, 196, 139, 137, 164, 43, 36, 238, 49, 14, 224, 68, 172, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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