Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ccb53851242983bd9751a2202f2278d47c4c92716f1a20ef6cef2d13d93e66b

Tx prefix hash: 4a639a86a3f59fc8e0f44280521e41f53c34d67bf5895174bca4ffbede725baa
Tx public key: 98f28cc3f57dfb77c9107c33c0532ebe0b6db5aabe8a7005ba9c138430987d86
Timestamp: 1576423092 Timestamp [UCT]: 2019-12-15 15:18:12 Age [y:d:h:m:s]: 05:342:19:10:21
Block: 27245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1389641 RingCT/type: yes/0
Extra: 0198f28cc3f57dfb77c9107c33c0532ebe0b6db5aabe8a7005ba9c138430987d860211000000039159db1e000000000000000000

1 output(s) for total of 498.581636706000 dcy

stealth address amount amount idx
00: 91ff63624a97139e7e595e53ea499d9d3bdce50116a57f79a73fcf64d2b7513c 498.581636706000 45218 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": 27255, "vin": [ { "gen": { "height": 27245 } } ], "vout": [ { "amount": 498581636706, "target": { "key": "91ff63624a97139e7e595e53ea499d9d3bdce50116a57f79a73fcf64d2b7513c" } } ], "extra": [ 1, 152, 242, 140, 195, 245, 125, 251, 119, 201, 16, 124, 51, 192, 83, 46, 190, 11, 109, 181, 170, 190, 138, 112, 5, 186, 156, 19, 132, 48, 152, 125, 134, 2, 17, 0, 0, 0, 3, 145, 89, 219, 30, 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