Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 648865a0eb6bf85b61e6213a4b991001ca0c6a60481bdd29ad7ae72907e34ed3

Tx prefix hash: 3750cd19e2510236ff7df96bc1c39c0171e13bf232f992e359374651948f54c7
Tx public key: 043c104dd8c073e9fa969bf52fa7ae2c6efb506deb70505403e02c0502946d52
Timestamp: 1614384238 Timestamp [UCT]: 2021-02-27 00:03:58 Age [y:d:h:m:s]: 03:305:14:07:49
Block: 207403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 977650 RingCT/type: yes/0
Extra: 01043c104dd8c073e9fa969bf52fa7ae2c6efb506deb70505403e02c0502946d5202110000000c9c1fbdcc000000000000000000

1 output(s) for total of 126.121281916000 dcy

stealth address amount amount idx
00: e45751852dcd0438e9f08fa8be30f3bfdf8fb35f6b6e06779ee43d83232aba7e 126.121281916000 423416 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": 207413, "vin": [ { "gen": { "height": 207403 } } ], "vout": [ { "amount": 126121281916, "target": { "key": "e45751852dcd0438e9f08fa8be30f3bfdf8fb35f6b6e06779ee43d83232aba7e" } } ], "extra": [ 1, 4, 60, 16, 77, 216, 192, 115, 233, 250, 150, 155, 245, 47, 167, 174, 44, 110, 251, 80, 109, 235, 112, 80, 84, 3, 224, 44, 5, 2, 148, 109, 82, 2, 17, 0, 0, 0, 12, 156, 31, 189, 204, 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