Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50807b58ee21c4fb7182c0ac9042e6f73721d8621615157eefda3c5504e2ee8c

Tx prefix hash: d9578fdf304682e008d870a795326a73026e247481ec70ed551a6789730b6f7a
Tx public key: 548e13bae5b19de0cc57c83e3562c0a6153c71b430e2e9e88f89205274dfe0c0
Timestamp: 1694656578 Timestamp [UCT]: 2023-09-14 01:56:18 Age [y:d:h:m:s]: 02:054:04:48:05
Block: 847630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558399 RingCT/type: yes/0
Extra: 01548e13bae5b19de0cc57c83e3562c0a6153c71b430e2e9e88f89205274dfe0c002110000000833af99f4000000000000000000

1 output(s) for total of 0.953783933000 dcy

stealth address amount amount idx
00: 1276ed77f248c9be66926a22caaaa4a5c47fd549fe453408b03e91beef1b6a34 0.953783933000 1301168 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": 847640, "vin": [ { "gen": { "height": 847630 } } ], "vout": [ { "amount": 953783933, "target": { "key": "1276ed77f248c9be66926a22caaaa4a5c47fd549fe453408b03e91beef1b6a34" } } ], "extra": [ 1, 84, 142, 19, 186, 229, 177, 157, 224, 204, 87, 200, 62, 53, 98, 192, 166, 21, 60, 113, 180, 48, 226, 233, 232, 143, 137, 32, 82, 116, 223, 224, 192, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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