Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c35fadb6aad58492cda1b1d5788be2c307ccae164aefc532c507d54f077d956

Tx prefix hash: 059d511de2aaadd31e4e963fb4b14e56cd16abe9194e84af2be7f4b79e460b2b
Tx public key: 5a9b859a52fcd272a826380cd367fbed04b30e7a770d932e6e0ab5b75ba4cae8
Timestamp: 1699392321 Timestamp [UCT]: 2023-11-07 21:25:21 Age [y:d:h:m:s]: 01:132:14:06:21
Block: 886712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355960 RingCT/type: yes/0
Extra: 015a9b859a52fcd272a826380cd367fbed04b30e7a770d932e6e0ab5b75ba4cae802110000000775e3f0e9000000000000000000

1 output(s) for total of 0.707872523000 dcy

stealth address amount amount idx
00: 5cbb6a0e81a4f32e70a22f5f5e5eea89a83cef9b364a746f8de57e0b13dfb572 0.707872523000 1342549 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": 886722, "vin": [ { "gen": { "height": 886712 } } ], "vout": [ { "amount": 707872523, "target": { "key": "5cbb6a0e81a4f32e70a22f5f5e5eea89a83cef9b364a746f8de57e0b13dfb572" } } ], "extra": [ 1, 90, 155, 133, 154, 82, 252, 210, 114, 168, 38, 56, 12, 211, 103, 251, 237, 4, 179, 14, 122, 119, 13, 147, 46, 110, 10, 181, 183, 91, 164, 202, 232, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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