Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6f6da2189f880b74d46a4526fe5b28179a96c7e67096f4ae086decb6fb484bd

Tx prefix hash: ec5dc4ec1286ecf32e96ec1e3674d65bf28975f2c73636a9be222ae617d0c1ed
Tx public key: a866b7f3ee5155d86db16a204457d37bddac87df95cedd047c85e984430adae1
Timestamp: 1688885735 Timestamp [UCT]: 2023-07-09 06:55:35 Age [y:d:h:m:s]: 01:232:02:23:47
Block: 799863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426973 RingCT/type: yes/0
Extra: 01a866b7f3ee5155d86db16a204457d37bddac87df95cedd047c85e984430adae1021100000005faf35c9c000000000000000000

1 output(s) for total of 1.373162619000 dcy

stealth address amount amount idx
00: 0cb87d3a61dbc4f425d6eb2a8696a800cbc7969916442dddacbcbec357d8fbfd 1.373162619000 1250896 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": 799873, "vin": [ { "gen": { "height": 799863 } } ], "vout": [ { "amount": 1373162619, "target": { "key": "0cb87d3a61dbc4f425d6eb2a8696a800cbc7969916442dddacbcbec357d8fbfd" } } ], "extra": [ 1, 168, 102, 183, 243, 238, 81, 85, 216, 109, 177, 106, 32, 68, 87, 211, 123, 221, 172, 135, 223, 149, 206, 221, 4, 124, 133, 233, 132, 67, 10, 218, 225, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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