Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73eb9836e37205dfaf5ddf0dc31e093feb802a6529a5a5f0e50a4902441034c1

Tx prefix hash: d9f9373bd12126d330779dce5e6c105cc55f1048aa4d2fbb58ab097e1f0941a6
Tx public key: 5c8d6d774a3688d1bfec058673d3de8684f90bb4455ed2ae3147db2f9a69f0db
Timestamp: 1719860891 Timestamp [UCT]: 2024-07-01 19:08:11 Age [y:d:h:m:s]: 00:279:18:50:00
Block: 1056399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199907 RingCT/type: yes/0
Extra: 015c8d6d774a3688d1bfec058673d3de8684f90bb4455ed2ae3147db2f9a69f0db0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd1a045572367c8dfa6d1ff57c165b384bf8bc1061d64fcfe2c54f5a879db763 0.600000000000 1526812 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": 1056409, "vin": [ { "gen": { "height": 1056399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd1a045572367c8dfa6d1ff57c165b384bf8bc1061d64fcfe2c54f5a879db763" } } ], "extra": [ 1, 92, 141, 109, 119, 74, 54, 136, 209, 191, 236, 5, 134, 115, 211, 222, 134, 132, 249, 11, 180, 69, 94, 210, 174, 49, 71, 219, 47, 154, 105, 240, 219, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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