Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f38f2180998cc8301bbce51ae43820164e967cf2fa9b0801cb5b4b8b71c8aae4

Tx prefix hash: 9456232c3c355f6ac9d74e7a11b2e7c0f08ecd0af1464d9871817e01249eeab7
Tx public key: bac7e4cee3b0109106a12a7475da6fca87650eacec9009f025886ebf1aaa0fb1
Timestamp: 1713670348 Timestamp [UCT]: 2024-04-21 03:32:28 Age [y:d:h:m:s]: 00:284:14:36:17
Block: 1005072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203448 RingCT/type: yes/0
Extra: 01bac7e4cee3b0109106a12a7475da6fca87650eacec9009f025886ebf1aaa0fb10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 970e0879e275d8c791f7c5da9983ae4864e460439af2cef64c897b95aaa8a3d1 0.600000000000 1465650 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": 1005082, "vin": [ { "gen": { "height": 1005072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "970e0879e275d8c791f7c5da9983ae4864e460439af2cef64c897b95aaa8a3d1" } } ], "extra": [ 1, 186, 199, 228, 206, 227, 176, 16, 145, 6, 161, 42, 116, 117, 218, 111, 202, 135, 101, 14, 172, 236, 144, 9, 240, 37, 136, 110, 191, 26, 170, 15, 177, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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