Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d500062b77e6f1495117931544a9fbff29fe7e33c0e9591409d32c71b1514d7

Tx prefix hash: 2ce4985c593b5894e156fe866b0ac9248a3eac4220a6b0697ce6aaeabe0555fa
Tx public key: f00f86f26f62dfb316124bf37ff937a463e6b4ba6702cb4c93e9331b9eb0cf8e
Timestamp: 1721613491 Timestamp [UCT]: 2024-07-22 01:58:11 Age [y:d:h:m:s]: 01:108:04:10:23
Block: 1070921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335822 RingCT/type: yes/0
Extra: 01f00f86f26f62dfb316124bf37ff937a463e6b4ba6702cb4c93e9331b9eb0cf8e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30c75af6e34ad1b549b36b5a472330d2ed25744a698039d7cdfcb605909ce7a3 0.600000000000 1542952 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": 1070931, "vin": [ { "gen": { "height": 1070921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30c75af6e34ad1b549b36b5a472330d2ed25744a698039d7cdfcb605909ce7a3" } } ], "extra": [ 1, 240, 15, 134, 242, 111, 98, 223, 179, 22, 18, 75, 243, 127, 249, 55, 164, 99, 230, 180, 186, 103, 2, 203, 76, 147, 233, 51, 27, 158, 176, 207, 142, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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