Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2b75c71e28863e1b1d0cd88bff09ac5f7c648c8893909e80ffeb2de4aa4e931

Tx prefix hash: e607963a5e009be8c0d29b3813efbac86aca3f868e7d4ab618a2dee7d72995df
Tx public key: 6d2543d6b84e3f700ed25af35ccd44618287e4f68eab8fae184a2844d015c9d2
Timestamp: 1734891342 Timestamp [UCT]: 2024-12-22 18:15:42 Age [y:d:h:m:s]: 00:091:08:27:28
Block: 1180922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65035 RingCT/type: yes/0
Extra: 016d2543d6b84e3f700ed25af35ccd44618287e4f68eab8fae184a2844d015c9d2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8966ca1c68e259aa6255d553b690b30734a552145255e6c76f899ecda7aabc44 0.600000000000 1667337 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": 1180932, "vin": [ { "gen": { "height": 1180922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8966ca1c68e259aa6255d553b690b30734a552145255e6c76f899ecda7aabc44" } } ], "extra": [ 1, 109, 37, 67, 214, 184, 78, 63, 112, 14, 210, 90, 243, 92, 205, 68, 97, 130, 135, 228, 246, 142, 171, 143, 174, 24, 74, 40, 68, 208, 21, 201, 210, 2, 17, 0, 0, 0, 1, 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