Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17d1d53f55b17c4cf503ec79b8891e6f3877b73b45c541d4054d47610793ae14

Tx prefix hash: 8c2fe35e96d76e596dfefae93986280d9a482c24e478e301170e2be550e78370
Tx public key: c177787d4327b0516a75840d5903c7f50e4cd71eebc3e9d766f1cbf80c626649
Timestamp: 1700262729 Timestamp [UCT]: 2023-11-17 23:12:09 Age [y:d:h:m:s]: 01:159:23:50:36
Block: 893928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375513 RingCT/type: yes/0
Extra: 01c177787d4327b0516a75840d5903c7f50e4cd71eebc3e9d766f1cbf80c62664902110000000733af99f4000000000000000000

1 output(s) for total of 0.669954704000 dcy

stealth address amount amount idx
00: 679a1f4767e1c9a0b018f9636096450652130abbf26b69d91389dfcf591c1337 0.669954704000 1350113 of 0

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": 893938, "vin": [ { "gen": { "height": 893928 } } ], "vout": [ { "amount": 669954704, "target": { "key": "679a1f4767e1c9a0b018f9636096450652130abbf26b69d91389dfcf591c1337" } } ], "extra": [ 1, 193, 119, 120, 125, 67, 39, 176, 81, 106, 117, 132, 13, 89, 3, 199, 245, 14, 76, 215, 30, 235, 195, 233, 215, 102, 241, 203, 248, 12, 98, 102, 73, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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