Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb1ea7c61074dba8d5b61479ae40438691660cc23e03480ad2661f0620740bb8

Tx prefix hash: dc5fcce6b45fbbf119382934405c04982d7e57220c0618a75032b1b61968714e
Tx public key: e1d6272418f8b4270fd4c3fb5840cdfbbb915d38c37835b51f754a4b3910aed2
Timestamp: 1677111748 Timestamp [UCT]: 2023-02-23 00:22:28 Age [y:d:h:m:s]: 01:327:05:15:20
Block: 702872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494805 RingCT/type: yes/0
Extra: 01e1d6272418f8b4270fd4c3fb5840cdfbbb915d38c37835b51f754a4b3910aed2021100000004faf35c9c000000000000000000

1 output(s) for total of 2.878015954000 dcy

stealth address amount amount idx
00: ed81cd81e40dad548f26ec6d7dc4436e92f23ef76811291f24254722c76a24fa 2.878015954000 1146427 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": 702882, "vin": [ { "gen": { "height": 702872 } } ], "vout": [ { "amount": 2878015954, "target": { "key": "ed81cd81e40dad548f26ec6d7dc4436e92f23ef76811291f24254722c76a24fa" } } ], "extra": [ 1, 225, 214, 39, 36, 24, 248, 180, 39, 15, 212, 195, 251, 88, 64, 205, 251, 187, 145, 93, 56, 195, 120, 53, 181, 31, 117, 74, 75, 57, 16, 174, 210, 2, 17, 0, 0, 0, 4, 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