Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6cc92c749963e044d51d66478b9a05c218becfdc0679defdc9166699f1dcb13

Tx prefix hash: 5349e6186dda312c3d3b7c36db6b48cafebd3cb096d2044784e00de47a57801a
Tx public key: 11812adf1c4be9a574ef3716fd2686ca9702917f322909fdf73f7f039b69d773
Timestamp: 1703315983 Timestamp [UCT]: 2023-12-23 07:19:43 Age [y:d:h:m:s]: 01:035:15:43:00
Block: 919234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286677 RingCT/type: yes/0
Extra: 0111812adf1c4be9a574ef3716fd2686ca9702917f322909fdf73f7f039b69d7730211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f6a2217627a2e457e28b8e3d8a3278be747861a74a1b44b3d8de2d855dc7ce5 0.600000000000 1376900 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": 919244, "vin": [ { "gen": { "height": 919234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f6a2217627a2e457e28b8e3d8a3278be747861a74a1b44b3d8de2d855dc7ce5" } } ], "extra": [ 1, 17, 129, 42, 223, 28, 75, 233, 165, 116, 239, 55, 22, 253, 38, 134, 202, 151, 2, 145, 127, 50, 41, 9, 253, 247, 63, 127, 3, 155, 105, 215, 115, 2, 17, 0, 0, 0, 7, 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