Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1c3253030afa5180c0aa460c65bddbd8d86ec7546ee022623f98c86d2560f44

Tx prefix hash: bc885af203b65ce5374755732adea98b27a6d555231a22963b02464ad9e7027a
Tx public key: 160b9c51ccb2b17dc00fe821ba5b7f4f1665c0693d516bc48d84625fc3fc97da
Timestamp: 1696024201 Timestamp [UCT]: 2023-09-29 21:50:01 Age [y:d:h:m:s]: 01:149:07:32:40
Block: 858988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367729 RingCT/type: yes/0
Extra: 01160b9c51ccb2b17dc00fe821ba5b7f4f1665c0693d516bc48d84625fc3fc97da0211000000044b8f5122000000000000000000

1 output(s) for total of 0.874613581000 dcy

stealth address amount amount idx
00: aeb7e9e11cbcbfd0c72403e8e53fe989774cb29e486b409cf64d4ed4f8accf8a 0.874613581000 1313192 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": 858998, "vin": [ { "gen": { "height": 858988 } } ], "vout": [ { "amount": 874613581, "target": { "key": "aeb7e9e11cbcbfd0c72403e8e53fe989774cb29e486b409cf64d4ed4f8accf8a" } } ], "extra": [ 1, 22, 11, 156, 81, 204, 178, 177, 125, 192, 15, 232, 33, 186, 91, 127, 79, 22, 101, 192, 105, 61, 81, 107, 196, 141, 132, 98, 95, 195, 252, 151, 218, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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