Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c171601f105b7d7adb797e1fab2b212653e45d24f358ab76ae2bbb2ff2f56d6

Tx prefix hash: f5ede001892516acf7e78868ab10710b90efc68b3f7f60cc2fa8a7056082d8e2
Tx public key: 4b95846e8347bb60c933554f49b5fd4a313f696bde89a7ab75ca5fb53b51a479
Timestamp: 1726601714 Timestamp [UCT]: 2024-09-17 19:35:14 Age [y:d:h:m:s]: 00:204:06:07:44
Block: 1112283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145811 RingCT/type: yes/0
Extra: 014b95846e8347bb60c933554f49b5fd4a313f696bde89a7ab75ca5fb53b51a479021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 575a1ee6084127711d1baa13c610218489a16017394b6c46ce40b09d37681224 0.600000000000 1591550 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": 1112293, "vin": [ { "gen": { "height": 1112283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "575a1ee6084127711d1baa13c610218489a16017394b6c46ce40b09d37681224" } } ], "extra": [ 1, 75, 149, 132, 110, 131, 71, 187, 96, 201, 51, 85, 79, 73, 181, 253, 74, 49, 63, 105, 107, 222, 137, 167, 171, 117, 202, 95, 181, 59, 81, 164, 121, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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