Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f475e8846e565fd84ffcbd71f77e08310c9e929a4eda92e57b61b27f6ae1d08

Tx prefix hash: 6af034d82b80410bbe8b1021e4c2f0ce75ae0214d0ccd803447471034082b24c
Tx public key: 9f4f8adbc754f6d9eb865f764c12bba3d19028e260b6ffc50232edcbd3b48fa5
Timestamp: 1732597011 Timestamp [UCT]: 2024-11-26 04:56:51 Age [y:d:h:m:s]: 00:118:18:03:03
Block: 1161894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84670 RingCT/type: yes/0
Extra: 019f4f8adbc754f6d9eb865f764c12bba3d19028e260b6ffc50232edcbd3b48fa5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0a5e79f65c21c24b2932f0d2816d6c02ce9c9c672a436ef2ba83afe4d2a9572 0.600000000000 1647549 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": 1161904, "vin": [ { "gen": { "height": 1161894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0a5e79f65c21c24b2932f0d2816d6c02ce9c9c672a436ef2ba83afe4d2a9572" } } ], "extra": [ 1, 159, 79, 138, 219, 199, 84, 246, 217, 235, 134, 95, 118, 76, 18, 187, 163, 209, 144, 40, 226, 96, 182, 255, 197, 2, 50, 237, 203, 211, 180, 143, 165, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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